Gold Medal Software 3/Gold Medal Software - Volume 3 (Gold Medal) (1994).iso/misc/namcln20.arj/NAMCLN20.TXT

Text File | 1994-02-14 | 13KB | 282 lines

                            NAMECLEAN
                    Version 2.0, 14 Feb 1994
        Copyright (c) 1992, 1993, 1994 by Jack J. Chandler

This release of NAMECLEAN has some major modifications which alter
the names in your NAME2.DAT file for entries into place fields
two, three, and four of your INDIV2.DAt and MARR2.DAT files.

The modifications are intended to assist you in preparing or
changing your place name entry formats to meet varying requirements
of 1) Publication, and 2) Submission to SLC.  An attempt was made
to retain the entry format of foreign locations while making the
appropriate changes to all US locations.

Options are:
  1> Adding the term 'Co.' to the county name in fields
     at levels two or three. Replaces the term 'County'
     with the term 'Co.'.

  2> Deleting the term 'Co.','Co','Co,' or the term 'County' from
     the county name in fields at levels two or three.

  3> Replacing the full state name with the two letter postal
     abbreviation as contained in the 'PAF Documentation
     Guidelines' 1993 edition by the Silicon Valley PAF Users
     Group in name field at levels three and four.

   4> Replacing the two letter postal with the full state name
      in name fields at levels three or four.

   5> Install 'USA' in level four for all United States areas
      that have a valid state name or two letter code in level
      three.

   6> Remove 'USA' in level four for all United States areas
      that have a valid state name or abbreviation in level
      three.

At any one pass three operations may be performed.  One each
for Counties, States, and USA.  Prior to selecting option 7>
to proceed with the processing, any of the selections may be
changed.  The '*' is placed to the left of the option that is
currently selected.  If an option is marked with the '*' it may
be de-selected by selecting that option again or by selecting
an alternate option in the same category.

Under option 1> the term 'Co.' will _not_ be added if it already
exists in the selected level.  If the addition of 'Co.' to the
county name exceeds the 16 character limit of PAF for names then
the county name is truncated to accommodate the addition of 'Co.'
without exceeding 16 characters.  If a county name is truncated
during the addition of the term 'Co.' and menu option 2> is later
selected to remove the term 'Co.' the county name will remain
truncated.  The original county name will not be restored.

Under option 1> the term 'Co.' will not be added if there is an
entry in level four other than 'USA'.  If the Burial/Christening
county is in level three, then for Burials/Christenings  the 'Co.'
will be added only if there is a valid state name or two letter
code in level 4.

Under option 2> the term 'Co.' or the term 'County' will _not_ be
deleted if it is found in the first four characters of the name in
the selected level.  This is to prevent removing 'Co.' from some
entries from foreign places such as 'Co. Essex' or 'Co. York'.
Under option 1> the term 'Co.' would _not_ be added to these entries.

County names cannot be modified in levels 1 or 4.  County names
will not be modified if a valid state name or two letter code
does not exist in the level immediately following the county
name.

Under option 3> the full spelling of the state name will replace
the existing two letter postal abbreviation entered for US States
and Territories, and for Canadian Provinces as outlined in the
above cited publication.  Several of these entries will exceed
the 16 character limit of PAF for names and the existing names
will be truncated to allow retain a trailing nul character in the
17th name position.

State names cannot be modified in levels 1 or 2.

Under all options the normal operation of NAMCLEAN in removing
unused names is preserved.

It is most probable that under most options there will be an
_increase_ shown in the size of the NAME2.DAT file.  Many of the
names being changed under these options are used in other name/
place fields and therefore the name being changed will _not_ be
deleted but the new name added. If the original unused names
exceed the names added, then there should be a decrease shown
otherwise an increase will be shown.

To run NAMCLN20.EXE in its usually mode without changing either
county or state entries, merely select item option 7> from the
menu.  Option Q> will exit the program without running.

Proper operation of NAMCLN20.EXE for desired results depends upon
the strict consistency of entering names in your Individual and
Marriage records.  There must be consistency in levels/fields for
names in each category.  The only deviation accommodated is for
the entry of place names in the burial/christening fields.  Whereas
the normal location for county names and state names are in levels
2 and 3 respectively, in the burial/christening fields they may be
entered in levels 3 and 4 respectively.

If level 3 is used for counties in the burial/christening fields,
then the state MUST be entered in level 4.  If there is no entry
in level 4 to match a state name or postal code, then there will
be no action on the request for 'Co.' add or delete in that burial/
christening entry.

If level 2 is used for counties in the burial/christening fields,
then the rules for level 4 entries for all other event place names
will apply.

For all locations within the United States, level 4 must be empty
or contain 'USA'.  Any other entry in level 4 except the state
entry allowed for burial/christening fields will be interpreted
as a Foreign location and the requested action for the 'Co.' entry
or delete will not be taken.

Full state names and/or the state postal codes as listed in the
SV-PAF-UG PAF Documentation Guidlines 1993 edition is used for
all state comparisons and conversions.

No 'Co.' entries are made for the state of Alaska.  Alaska has
'Boroughs' instead of 'Counties'.

Louisiana has Parishes.  The term ' Par.' is inserted/deleted for
Louisiana instead of ' Co.'.  If the terms ' Parish', ' PAR', or
' Par' is in the field it will be accepted as ' Par.' and deleted if
menu option 2> is selected.  If one of those terms is in the field
when menu option 1> is selected it will be corrected to 'Par.'.


No 'Co.' entries are made for the Territories however all states
and territories with the exception of 'Canal Zone' will have
the 'USA' inserted in level 4 if requested.

If you have a database with mixed entry levels for your christening
and burials, i.e., some with counties in level2 and some with
level 3, some success can be had by running the program twice.
First run with counties selected in level2.  Then run with the
counties in level3.  There will be a problem only in those
locations where there is a county name that is the same as
a state name such as Utah, UT  or New York, NY  or Nevada, CA.
This should leave a smaller number of errors that running with
only a one level option.  Again, the program depends upon a
consistent pattern of level selections for your place names.

NAMCLN20 has been tested and found to operate as designed on a
database containing consistent field level selections for the
counties and states as described in the PAF users manual.

NAMCLN20 incorporates all features of versions 1.2b including
the correction of the format problem with the re-entry of case
changed names into the NAME2.DAT file as discussed below.  If
the NAME2.DAT file is increased in size, it will report ADDED
names rather than negative DELETED names.

The inclusion of these additional options in NAMCLEAN has
increased the size of the file considerably and has also
increased the run time.  The time now required will be from
the original time required by NAMCL12  if only item 7> is
selected, or up to about 200 place names/minute if all three
operation options are selected.

One current 'bug' or characteristic remaining in NAMCLN20 is
the inconsistent failure to process approximately 1.3% of the
state names when changing the full name to the two letter code
with menu option 3>.  A second run selecting only menu option 3>
will process the remaining names with no problem.  This problem
is being addressed and it is hoped that a future version will
correct the errors.

Previous version history:

Version 1.2b modifies code structure to prevent problems
when using on database in which name case changes have
been made with PAF2.2 or PAF2.3.  When the case of a name
is changed the new entry is not formatted properly when written
back to the NAME2.DAT file.

This improper format has no effect on the proper operation
of FR.EXE and other utilities included in the PAF packet.
It is not compatible with NAMCLN12.

If NAMCLN12 or NAMCL12A is used on this database, it will
display a _deletion_ of -n records where the n will represent
the number of times the changed name occurred in the data
base.  This will be for each name changed.  The -n indicates
an _addition_ of names to the NAME2.DAT file.

Running NAMCLN12 or NAMCL12A a second time will remove the
names added by the first pass.

NAMCL12B corrects the improper format of the entry and enters
no extraneous name.  If FR2.3 is later modified to correct this
bug, then NAMCL12B will still function properly.

The original NAMCLEN1 will handle the improper format satisfactorily
but does not correct the format in the NAME2.DAT file.

Version 1.2 corrects potential problem on handling large
databases with NAME2.DAT record numbers greater than 32767.

NAMCLEAN is a PAF utility to remove unused names from you
PAF NAME2.DAT file.

NAMCLEAN is extremely easy to use and requires only normal
precautions to protect your files from damage during the
process.  A good current backup should always be made prior
to modification by any software that changes or writes to your
database.

The files that require backups are NAME2.DAT, INDIV2.DAT, and
MARR2.DAT.  The other files in your database are not effected.

NAMCLEAN can be ran from any location.  Processing speed will
be enhanced if the three files NAME2.DAT, INDIV2.DAT, and
MARR2.DAT are in a ram-drive or on your hard drive.  File access
will greatly increase processing time if those files are on a
floppy disk.

There must be sufficient space left in the location of your data
files to create a .TMP file the size of your NAME2.DAT file.
This .TMP file is erased upon termination of the program.

Run FRCHK on your original files prior to running NAMCLEAN.  If
FRCHK reports problems, then attempt to correct them prior to
running NAMCLEAN.  If you have the 10 June 1990 or later update
to PAF 2.2, you can run FRCHK -f.  This will repair most minor
problems.  The results of NAMCLEAN are unpredictable if your
data fails the FRCHK.

Be sure that you enter the correct location of your data files
and that you use ^P to answer the prompt after the caution
warning.

Processing time for NAMCLEAN is much faster than using GEDCOM
procedures to clean up the NAME2.DAT file.  NAMCLEAN used in
conjunction with RECLAM14 will process my database of 5400
INDIV2.DAT, 2113 MARR2.DAT, and 3600 NAME2.DAT records in about
50 minutes on my 8mhz machine.  GEDCOM takes over 3 1/2
hours to complete this same function.

Processing time is dependent upon the number of name field
entries in your INDIV2.DAT and MARR2.DAT files.  INDIV2.DAT has
24 name fields.  MARR2.DAT has 5 name fields.  This means that
NAMCLEAN accesses, checks, and modifies if necessary 139,253
name pointers in those two files.  It also accesses, cross checks
for duplicity, and writes 3600 names to a new NAME2.DAT file.

NAMCLEAN does not modify any RIN or MRIN numbers.

                      *** NOTE ***

NAMCLEAN modifies your PAF data.  Be sure you have a current
backup before running NAMCLEAN.

                      ************

No registration of NAMCLEAN is required but a small donation of
up to $5.00 would be appreciated if you find this utility of use
to you.  If you request this from the author, please include an
additional $2.00 for postage and handling.

Send donations, comments, and questions to:

                   Jack Chandler
                   812 Vermillion Dr.
                   Henderson, NV  89015

Or contact on GEnie address J.CHANDLER2, or Jack Chandler on Fidonet
NGC GENEALOGY or GENSOFT echos.